Conversation
CMS_SignedInfo structure can not be created or freed, as it is just a pointer into CMS_ContentInfo stack.
0366ce3 to
b7f68eb
Compare
1c49e30 to
156f8df
Compare
Contributor
Author
|
@hsbt I would appreciate any pointers on how to debug the memory leak that the travis-ci build discovered. |
|
any plans to add cms support or pointers to working implementations? |
Contributor
Author
|
Replaced by #917 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the beginnings of support for CMS signatures and verification, in the spirit of the PKCS7 work.
I don't need encrypt/decrypt, so I will leave them for last. I will be adding eContentType settings, which are new since PKCS7. The OpenSSL CMS SignerInfo code works differently than the PKCS7_SIGNER_INFO, and as I don't need multiple signatures for the moment, I will leave that until later as well.